You are here: Job and Form Set Rules Reference > JDT Rules Reference > BatchingByPageCountPerRecipINI > INI File Examples > Scenario 4

Scenario 4

Like the Scenario 3, this scenario sends form sets to agent batches depending on the number of pages. This scenario, however, uses a GVM variable as the condition and an XML extract file. In the AFGJOB.JDT, you must first create the global variable you are going to use for the condition. In this scenario, it is called AGT1. To create it, use the CreateGlbVar rule. Then, use the Ext2GVM rule to map the data to the GVM variable named AGT1. This rule is placed after the LoadExtractData rule in the AGFJOB.JDT file. If the GVM variable (AGT1) holds a value, the condition is considered true and the transaction is written to the appropriate batch by the page count. If the GVM variable (AGT1) does not hold a value, the condition is considered false and the transaction will be written to the Default batch. Here is an example:

/* This base (this implementation) uses these rules. */

<Base Rules>

;RULStandardJobProc;1;Always the first job level rule;

;SetErrHdr;1;*:;

;SetErrHdr;1;*:------------------------------------------------;

;SetErrHdr;1;*: FormMaker Data Generation (Base);

;SetErrHdr;1;*: ;

;SetErrHdr;1;***: Transaction: ***PolicyNum***;

;SetErrHdr;1;***: Symbol: ***Symbol***;

;SetErrHdr;1;***: Module: ***Module***;

;SetErrHdr;1;***: State: ***State***;

;SetErrHdr;1;***: Company Name (after ini conversion): ***Company***;

;SetErrHdr;1;***: Line of Business (after ini conversion): ***Lob***;

;SetErrHdr;1;***: Trans Type: ***TransactionType***;

;SetErrHdr;1;***: Run Date: ***Rundate***;

;SetErrHdr;1;*:------------------------------------------------;

;CreateGlbVar;1;TXTLst,PVOID;

;CreateGlbVar;1;TblLstH,PVOID;

;CreateGlbVar;1;AGT1,CHAR_ARRAY,15;

;JobInit1;1;;

;LoadDDTDefs;1;;

;InitOvFlw;1;;

;LoadTextTbl;1;;

;LoadTblFiles;1;;

;SetOvFlwSym;1;CGDECBDOVF,Q1GDBD,5;

;BuildMasterFormList;1;4;

<Base Form Set Rules>

;RULStandardTransactionProc;2;Always the first transaction level rule;

;LoadExtractData;2;;

;GetCo;2;11,HEADERREC 35,3;

;GetLOB;2;11,HEADERREC 40,3;

;Ext2Gvm;2;!/COMPANY/FORMS/FORM/SECTION/FIELDS/AGENTNAME 1,15,AGT1;

;ResetOvFlw;2;;

;BuildFormList;2;;

;LoadRcpTbl;2;;

;UpdatePOLFile;2;;

;RunSetRcpTbl;2;;

;BatchingByPageCountPerRecipINI;;;

Here is an example of the FSISYS.INI file:

< BatchingByRecip >

DefaultBatch = Default

Batch_Recip_Def = =GVM("AGT1"),;"AGENTNAME1PAGE";AGENT

Batch_Recip_Def = =GVM("AGT1"),;"AGENTNAMEMULTIPAGE";AGENT

Batch_Recip_Def = Manual;"MANUAL";ALL

Batch_Recip_Def = Error;"ERROR";ALL

< Default >

Printer = PDefault

If the GVM variable holds a value, the system sends all one-page transactions to an Agent batch specifically for one-page form sets:

< AgenName1Page >

Printer = Printer1

PageRange = 1,1

If the GVM variable holds a value, the system sends all transactions that are more than one page to an Agent batch designed to hold form sets that consist of two or more pages:

< AgentNameMultipage >

Printer = Printer2

PageRange = 2,99999

Form sets that go into WIP are put in the manual batch:

< Manual >

Printer = Printer3

PageRange = 1,99999

Form sets with errors go into the error batch:

< Error >

Printer = Printer4

PageRange = 1,99999

This excerpt shows how to set the Print_Batches, PrinterInfo, and PrintedOutputFile control groups:

< Print_Batches >

Default = default.bch

AgentName1Page = agentname1page.bch

AgentNameMultipage = agentnamemultipage.bch

Manual = manual.bch

Error = error.bch

< Printer1 >

Port = data\agentname1page.pcl

< Printer2 >

Port = data\agentnamemultipage.pcl

< Printer3 >

Port = data\manual.pcl

< Printer4 >

Port = data\error.pcl

< PDefault >

Port = data\pdefault

< PrinterInfo >

Printer = Printer1

Printer = Printer2

Printer = Printer3

Printer = Printer4

Printer = PDefault